Kindle End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Kindle versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Kindle Scribe Colorsoft (1st Generation) is supported until December 31, 2030, its end-of-support date. The next Kindle version to reach end of life is (10th Generation), on December 31, 2026. 15 of 27 tracked Kindle versions are past end of life; the most recent to reach it, Oasis (9th Generation), did so on June 1, 2024. The full Kindle lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| Kindle (1st Generation) | 1.2.1 | Nov 19, 2007 | Not published | Past EOL | EOL |
| Kindle (2nd Generation) | 2.5.8 | Feb 23, 2009 | Not published | Past EOL | EOL |
| Kindle DX (2nd Generation) | 2.5.8 | Jun 10, 2009 | Not published | Past EOL | EOL |
| Kindle Keyboard (3rd Generation) | 3.4.3 | Aug 27, 2010 | Not published | Past EOL | EOL |
| Kindle Touch (4th Generation) | 5.3.7.3 | Sep 28, 2011 | Not published | Past EOL | EOL |
| Kindle (4th Generation) | 4.1.4 | Sep 28, 2011 | Not published | Past EOL | EOL |
| Kindle (5th Generation) | 4.1.4 | Sep 6, 2012 | Not published | Past EOL | EOL |
| Kindle Paperwhite (5th Generation) | 5.6.1.1 | Oct 1, 2012 | Jun 26, 2015 | 4105 days past EOL | EOL |
| Kindle Paperwhite (6th Generation) | 5.12.2.2 | Sep 30, 2013 | Oct 1, 2019 | 2547 days past EOL | EOL |
| Kindle (7th Generation) | 5.12.2.2 | Oct 2, 2014 | Oct 1, 2019 | 2547 days past EOL | EOL |
| Kindle Voyage (7th Generation) | 5.13.6 | Nov 4, 2014 | Apr 1, 2021 | 1999 days past EOL | EOL |
| Kindle Paperwhite (7th Generation) | 5.16.2.1.1 | Jun 30, 2015 | Jun 1, 2024 | 842 days past EOL | EOL |
| Kindle Oasis (8th Generation) | 5.16.2.1.1 | Apr 27, 2016 | Jun 1, 2024 | 842 days past EOL | EOL |
| Kindle (8th Generation) | 5.16.2.1.1 | Jun 22, 2016 | Jun 1, 2024 | 842 days past EOL | EOL |
| Kindle Oasis (9th Generation) | 5.16.2.1.1 | Oct 31, 2017 | Jun 1, 2024 | 842 days past EOL | EOL |
| Kindle Paperwhite (10th Generation) | 5.18.1 | Nov 7, 2018 | Dec 31, 2026 | 101 days remaining | Warning |
| Kindle (10th Generation) | 5.18.1 | Apr 10, 2019 | Dec 31, 2026 | 101 days remaining | Warning |
| Kindle Oasis (10th Generation) | 5.18.2 | Jul 24, 2019 | Dec 31, 2028 | 832 days remaining | Active |
| Kindle Paperwhite (11th Generation) | 5.19.2 | Oct 27, 2021 | Dec 31, 2028 | 832 days remaining | Active |
| Kindle (11th Generation) - 2022 Release | 5.19.2.0.1 | Sep 13, 2022 | Dec 31, 2028 | 832 days remaining | Active |
| Kindle Scribe - 2022 Release | 5.19.6 | Nov 30, 2022 | Dec 31, 2029 | 1197 days remaining | Active |
| Kindle (11th Generation) - 2024 Release | 5.19.2.0.1 | Oct 16, 2024 | Dec 31, 2030 | 1562 days remaining | Active |
| Kindle Paperwhite (12th Generation) - 2024 Release | 5.19.6 | Oct 16, 2024 | Dec 31, 2030 | 1562 days remaining | Active |
| Kindle Colorsoft (1st Generation) | 5.19.6 | Oct 30, 2024 | Dec 31, 2030 | 1562 days remaining | Active |
| Kindle Scribe - 2024 Release | 5.19.6 | Dec 4, 2024 | Dec 31, 2029 | 1197 days remaining | Active |
| Kindle Scribe Colorsoft (1st Generation) | 5.19.6 | Sep 30, 2025 | Dec 31, 2030 | 1562 days remaining | Active |
| Kindle Scribe (3rd Generation) | 5.19.6 | Sep 30, 2025 | Dec 31, 2030 | 1562 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/kindle)
Kindle release and support pattern
Of the 27 release lines tracked, 15 are past end of life and 12 are still within support; 7 are marked end of life without a published date. The newest line, kindle-scribe-3, was released September 30, 2025. The next scheduled end of life is kindle-10 on December 31, 2026 — 100 days from this build. The longest-supported line currently published is kindle-11-2024, to December 31, 2030.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Kindle end of life mean for your organization?
When a version of Kindle reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Kindle should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Kindle reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for Kindle from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →